Skip to content

Conversation

@bchampp
Copy link
Member

@bchampp bchampp commented Nov 13, 2025

Issue #, if available:

Description of changes:
Callback IDs are encoded over the wire since they're sent as a URL parameter. We need to decode them in the router layer.

Dependencies

If this PR requires testing against a specific branch of the Python Language SDK (e.g., for unreleased changes), uncomment and specify the branch below. Otherwise, leave commented to use the main branch.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Copy link
Contributor

@wangyb-A wangyb-A left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the checkpoint id get encoded when sending the request? or during ser / des ?

Because we also have similar pattern for GetDurableExecutions / checkpoint, where we do not see the quote pattern

@bchampp
Copy link
Member Author

bchampp commented Nov 13, 2025

Does the checkpoint id get encoded when sending the request? or during ser / des ?

Because we also have similar pattern for GetDurableExecutions / checkpoint, where we do not see the quote pattern

It gets encoded because it's part of a URL parameter -- not the case for Checkpoint or GetDurableExecution because those have the execution ARN in the route.

@bchampp bchampp merged commit 1e327b8 into main Nov 13, 2025
32 checks passed
@bchampp bchampp deleted the fix/decode-callback-id-routes branch November 13, 2025 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants